Hybrid SDN controller

ABSTRACT

One embodiment provides a network interface controller. The network interface controller includes a portion of a hybrid software-defined networking (“SDN”) controller, the portion of the hybrid SDN controller including a service abstraction layer module (“SAL”) and a southbound application programming interface (“SB API”), the SAL including a representation of a physical network.

FIELD

This disclosure relates to an SDN (Software-Defined Networking)controller, and, more particularly, to a hybrid SDN controller.

BACKGROUND

Generally, conventional networks include a plurality of interconnectednetwork devices, e.g., switches, routers, etc., that are each configuredto receive and to forward packets and/or frames according to respectiveinternal settings. These internal settings are generally configured atprovisioning and may require physical access to the network device inorder to change settings. In some cases, the configurations may beproprietary. Further, the network devices are typically configured withonly a local view of a portion of the network, e.g., for faulttolerance. Each network device is configured to make routing and/orforwarding decisions based on this local view. Thus, such networkdevices may not be responsive to dynamically changing network traffic,changes to node(s) coupled to the network nor to mobility of userdevices connected to the network.

Software-defined networking (SDN) is intended to address many of thesecharacteristics of such conventional network architectures. SDN isdesigned to decouple the data plane (i.e., the network devices) from thecontrol plane (e.g., routing decision rules and policies). In SDN, thecontrol plane may be centralized and/or may be distributed and the dataplane includes a plurality of interconnected network devices that areremotely programmable by the control plane.

An SDN controller may be configured to monitor network traffic and/orstate(s) of the node(s). The SDN controller may execute on a serverlocated at a data center, for example. The SDN controller is configuredto have a centralized global view of the network and is furtherconfigured to program the network devices dynamically, based, at leastin part, on network traffic, state(s) of the node(s) and/or policies setby, e.g., network administrators. The network devices are generallyconfigured with a standardized programming interface making programmingand reprogramming them relatively straightforward and not restricted tovendor-specific protocols. Thus, a SDN network architecture isconfigured to be dynamically reprogrammable by SDN controllers based, atleast in part, on business enterprise policies.

SDN controllers are typically implemented as a computer programexecuting on, for example, a server in a data center. The server mayinclude a host and a network interface coupled to the host. An SDNcontroller is typically configured to perform SDN controller operationson the host and to transmit and/or receive network-related data via thenetwork interface. The SDN controller may include a plurality ofarchitectural elements configured to facilitate monitoring and controlof the physical network and its associated network devices. Theseelements of an SDN controller may typically be written in a relativelyhigh level object-oriented language such as Java. For example,networking logic, i.e., creating objects and making logical decisionsbased on policies, are generally easier to implement in a high-levellanguage.

For example, the policies may be written in an extensible markuplanguage (XML) configured to encode the policies in a format that isboth human-readable and machine-readable. It is generally desirable forthe SDN controller elements “closest” to the network devices to beefficiently coded. High level computer languages are typically designedfor ease of programming and/or readability rather than efficiency, thus,generating efficient executable code for SDN controller elements closerto network devices may take considerable time and effort.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of embodiments of the claimed subject matterwill become apparent as the following Detailed Description proceeds, andupon reference to the Drawings, wherein like numerals depict like parts,and in which:

FIG. 1 illustrates an example network system consistent with variousembodiments of the present disclosure;

FIG. 2 illustrates an example host consistent with various embodimentsof the present disclosure;

FIG. 3 illustrates an example network interface controller consistentwith one embodiment of the present disclosure;

FIG. 4 illustrates an example workstation consistent with variousembodiments of the present disclosure;

FIG. 5 illustrates another example network interface controllerconsistent with one embodiment of the present disclosure;

FIG. 6 illustrates a flowchart of example operations of a hybridsoftware-defined networking (SDN) controller consistent with anembodiment of the present disclosure;

FIG. 7 illustrates another flowchart of example operations of a hybridSDN controller consistent with an embodiment of the present disclosure;and

FIG. 8 illustrates another flowchart of example operations of a hybridSDN controller consistent with an embodiment of the present disclosure.

Although the following Detailed Description will proceed with referencebeing made to illustrative embodiments, many alternatives,modifications, and variations thereof will be apparent to those skilledin the art.

DETAILED DESCRIPTION

Generally, this disclosure is related to a hybrid SDN (Software DefinedNetworking) controller. As used herein, a hybrid SDN controllercorresponds to an SDN controller that has a first portion configured tobe implemented on a host included in a computing device, e.g., a server,and a second portion configured to be implemented on a network interface(i.e., a network interface controller (“NIC”)) included in the computingdevice. The first portion of the hybrid SDN controller may includenorthbound Application Programming Interface(s) (API(s)), and networkinglogic (i.e., network service functions, network orchestration functionsand network management functions). The second portion of the hybrid SDNcontroller may include a southbound API and a service abstraction layer(e.g., SAL module) that includes a representation of the physicalnetwork.

Thus, a NIC consistent with various embodiments of the presentdisclosure is configured as a functional unit that includes networkinterface functionality as well as the portion of the hybrid SDNcontroller that includes the service abstraction layer and thesouthbound API. The service abstraction layer and southbound API may beefficiently coded. For example, the SAL module and southbound API may beprovided with the NIC by and/or on behalf of, e.g., an originalequipment manufacturer (OEM). In some embodiments, custom module(s)related to the southbound API may be implemented by an enterprise. Thecustom module(s) may be generated using, e.g., libraries provided by anOEM. Implementing the service abstraction layer and southbound API onthe NIC is further configured to reduce processing load on the host.Networking logic may continue to be coded in a high level objectoriented language without affecting the NIC programming. Distributingthe SDN control functions between the host and the NIC is configured tobe transparent to application(s) executing on node(s) in the physicalnetwork.

FIG. 1 illustrates an example network system 100 consistent with variousembodiments of the present disclosure. The system 100 generally includesa computing device 102 and a physical network 104. The system 100 mayinclude a workstation 110 configured to provide a user interface tofacilitate programmability of the hybrid SDN controller 120, asdescribed herein. The computing device 102 is configured to communicatewith the physical network 104. For example, the computing device 102 maybe a server in, e.g., a data center configured to manage the physicalnetwork 104 using a hybrid SDN controller, as described herein.

Physical network 104 may include at least one node 106 a, . . . , 106 nand a plurality of interconnected network devices 108 a, . . . , 108 n.Physical network 104 is configured to couple each node 106 a, . . . ,106 n to each other node 106 a, . . . , 106 n. “Node” may represent acomputer node element (e.g., host server system, desktop computer,laptop computer, tablet computer, etc.), switch, router, hub, networkstorage device, network attached device, non-volatile memory (NVM)storage device, cloud-based server and/or storage system, a blade, asmartphone, a feature phone, etc. Node(s) 106 a, . . . , 106 n may be atfixed location(s) and/or may be mobile. Network devices 108 a, . . . ,108 n may include switch(es), bridge(s), router(s) (wired and/orwireless). At least some of the network devices 108 a, . . . , 108 n areconfigured to be accessed and/or programmed by, e.g., computing device102, as described herein. The programmability, related to SDN, isconfigured to modify a behavior, e.g., routing behavior, of the networkdevice 108 a, . . . , 108 n.

Each node 106 a, . . . , 106 n may include at least one respectiveapplication 107 a, . . . , 107 n. The applications 107 a, . . . , 107 nare configured to communicate (e.g., transfer packets that include data)between nodes 106 a, . . . , 106 n via physical network 104. Theapplications 107 a, . . . , 107 n may be configured to request, e.g.,routing and/or path characteristics from hybrid SDN controller 120based, at least in part, on a type of data included in the packets. Forexample, voice and/or video data may correspond to a low latency path.The hybrid SDN controller 120 may then be configured to establish anappropriate path and to route packets from the requesting applicationalong this path.

The computing device 102 and the node(s) 106 a, . . . , 106 n maycommunicate with each other using a switched fabric communicationsprotocol, for example, an Ethernet communications protocol, Infinibandcommunications protocol, etc. The Ethernet communications protocol maybe capable of providing communication using a Transmission ControlProtocol/Internet Protocol (TCP/IP). The Ethernet protocol may comply orbe compatible with the Ethernet standard published by the Institute ofElectrical and Electronics Engineers (IEEE) titled “IEEE 802.3Standard”, published in March, 2002 and/or later versions of thisstandard, for example, the IEEE 802.3 Standard for Ethernet, published2012. The Infiniband protocol may comply or be compatible with theInfiniband specification published by the InfiniBand Trade Association(IBTA), titled “InfiniBand™ Architecture Specification”, Volume 1,Release 1.2.1, published June 2001 and/or later versions of thisspecification, for example, InfiniBand™ Architecture, Volume 1 (GeneralSpecification), Release 1.2.1, published January 2008 and Volume 2(Physical Specification), Release 1.3, published November 2012. Ofcourse, in other embodiments, the switched fabric communicationsprotocol may include a custom and/or proprietary switched fabriccommunications protocol.

Physical network 104 may include any packet-switched network such as,for example, Ethernet networks as set forth in the IEEE 802.3 standardand/or a wireless local area network such as, for example, IEEE 802.11standard. The wireless protocol may comply or be compatible with theWireless standard published by the IEEE titled “802.11-2012— IEEEStandard for Information technology—Telecommunications and informationexchange between systems Local and metropolitan area networks—Specificrequirements Part 11: Wireless LAN Medium Access Control (MAC) andPhysical Layer (PHY) Specifications”, published April 2012, and/or laterversions of this standard.

The computing device 102 generally includes a host 105 and a networkinterface 116. The computing device 102 further includes a hybrid SDNcontroller 120 consistent with various embodiments of the presentdisclosure. The hybrid SDN controller 120 includes a first portion 122and a second portion 124. The first portion 122 is configured to beimplemented on the host 105. The second portion 124 is configured to beimplemented on the network interface 116.

FIG. 2 illustrates an example host 205 consistent with variousembodiments of the present disclosure. The host 205 generally includes aprocessor 210, a bridge chipset 212 and a system memory 214. Theprocessor 210 is configured to perform operations associated withcomputing device 202 and host 205. Processor 210 may include one or moreprocessing unit(s), e.g., core(s). The bridge chipset 212 is configuredto couple the host 205 to a network interface, e.g., network interface116. In an embodiment, the bridge chipset 212 may be coupled to theprocessor 210. In this embodiment, the bridge chipset 212 may also becoupled to the system memory 214. In another embodiment, the bridgechipset 212 may be included in the processor 210. In this embodiment,the processor 210 (and bridge chipset 212) may also be coupled to thenetwork interface 116.

Host memory 214 is configured to store an operating system OS 230,policies 235 and SDN modules 236. SDN modules 236 corresponds to thefirst portion 122 of a hybrid SDN controller, consistent with variousembodiments of the present disclosure. In some embodiments, host memory214 may be configured to store an application 234. SDN modules 236 mayinclude northbound API 240, network service functions 242, networkorchestration functions 244 and network management functions 246. Insome embodiments, SDN modules 236 may include agent 252 configured toprovide customization and/or update capability, as described herein. Thehost memory 214 may be further configured to store a virtual machinemonitor (VMM) 232 and may then include a plurality of virtual machines(not shown). The host memory 214 may be configured to store a networkstack 231. The network stack 231 may be managed by OS 230. OS 230 may beconfigured to utilize a software framework configured for efficient andrelatively fast packet processing. For example, the software frameworkmay comply or be compatible with the Data Plane Development Kit (DPDK)configured to optimize packet processing on Intel® Architectureprocessors. Of course the Intel® Architecture is only an exampleimplementation and, in other embodiments, the teachings presented hereinmay be used for other core architecture technologies as may be providedby, for example, Motorola®, Apple®, . . . etc.

Host memory 214 may further include NIC driver 216 and I/O memory 218.I/O memory 218 may include one or more queue(s) 220. NIC driver 216, I/Omemory 218 and/or queue(s) 220 may be utilized for transfer and storageof packets and/or data between host 205 and the network interface.

Northbound (NB) API 240 is configured to provide an applicationsprogramming interface between application(s), e.g., application(s) 107a, . . . , 107 n and/or application 234 and network service functions242, network orchestration functions 244 and/or network managementfunctions 246. Network service functions 242 may include, for example,setting specific routes and paths in the network devices 108 a . . . 108n in the physical network 104. Network orchestration functions 244 mayinclude, for example, making decisions based on a view of the entirenetwork 104. Network orchestration functions 244 may be configured toutilize network service functions in order to enforce policies 235.Network management functions 246 may include, for example, turning on oroff ports and/or portions (e.g., circuit boards, processors, ASICs,etc.) of the network devices 108 a . . . 108 n included in the physicalnetwork 104.

Host SDN modules 236 are configured to perform networking logicoperations related to management, configuration and reconfiguration ofphysical network 104 and network device(s) 108 a, . . . , 108 n based onpolicies 235, network traffic and/or network topology changes. Policiesmay be related to, e.g., high availability (such as fail over paths androutes) and paths with specific requirements for specific applications.For example, a specific path in physical network 104 may be configuredto be low latency so that if an application, e.g., application 107 a ofFIG. 1, is streaming video or voice, the application 107 a would beassigned this low latency path. Applications 107 a, . . . , 107 n and234 may be configured to utilize northbound API 240 in order to accessSDN functions, e.g., network service functions 242, networkorchestration functions 244 and/or network management functions 246.These SDN functions may be filtered based on the policies 235. Thus,applications 107 a, . . . , 107 n and 234 are configured to use NB API240 as in a conventionally configured SDN controller that has all of theSDN controller elements included in host memory.

FIG. 3 illustrates an example network interface controller 316consistent with one embodiment of the present disclosure. First networkinterface controller 316 is configured to couple a computing device,e.g., computing device 102 (and a host, e.g., host 105) to a physicalnetwork, e.g., physical network 104 and thereby to node(s) 106 a, . . ., 106 n and network device(s) 108 a, . . . , 108 n. First networkinterface controller 316 includes processor 318, host interface 320,media access control (MAC) circuitry 322, physical layer circuitry (PHY)323 and NIC memory 324. Processor 318 is configured to performoperations associated with first network interface controller 316. Insome embodiments, processor 318 may correspond to a general purposeprocessor and may include a plurality of processing units. Hostinterface 320 is configured to couple first network interface controller316 to, e.g., bridge chipset 212 of FIG. 2. Host interface 320 mayinclude a media access controller (“MAC”) 321 configured to couple firstnetwork interface controller 316 to, e.g., host 205 via bridge chipset212 using, for example, a PCIe (Peripheral Component InterconnectExpress) communications protocol. The PCIe communications protocol maycorrespond to or be compatible with the PCIe 3.0 specification,published by the PCI-SIG (PCI Special Interest Group), titled “PCIExpress Base 3.0 Specification”, released November 2010, and/or laterversions of this specification.

MAC 322 and PHY 323 are configured to couple computing device 102 to,e.g., physical network 104. MAC 322 is configured to perform mediaaccess management for transmit and receive functions. PHY circuitry 323includes transmit circuitry configured to transmit data and/or messagepackets and/or frames to the physical network 104 including node(s) 106a, . . . , 106 n and network devices, 108 a, . . . , 108 n. PHYcircuitry 323 includes receive circuitry configured to receive data andor message packets and/or frames from the physical network 104. Ofcourse, PHY circuitry 323 may also include encoding/decoding circuitryconfigured to perform analog-to-digital and digital-to-analogconversion, encoding and decoding of data, analog parasitic cancellation(for example, cross talk cancellation), and recovery of received data.

First NIC 316 includes OS 360 and NIC SDN modules 362 and may includenetwork stack 361. NIC SDN modules 362 correspond to the second portion324 of a hybrid SDN controller, consistent with various embodiments ofthe present disclosure.

NIC SDN modules 362 include service abstraction layer module SAL 364 andsouthbound application programming interface SB API 368. NIC SDN modules362 may include libraries 337. Libraries 337 includes functional modulesthat may be utilized in generating custom modules and/or customprotocols, as described herein. Libraries 337, SAL 364 and SB API 368may be supplied by and/or on behalf of, e.g., an OEM of NIC 316. The SAL364 and SB API 368 may be optimized for, e.g., execution efficiency. OS360 is configured to manage operations of first NIC 316. The SAL 364includes a representation of the physical network 366. Therepresentation of the physical network 366 may include data structuresrelated to configuration of the physical network 104. For example, thedata structures may include number, type, location, interconnectionand/or settings for each network device 108 a, . . . , 108 n. The datastructures may further include data related to node(s) 106 a, . . . ,106 n, e.g., identifier, location, etc.

SB API 368 includes application programming interfaces configured to beutilized for communicating with network device(s) 108 a, . . . , 108 nin order to access and/or change the configuration of physical network104. In an embodiment, SB API 368 may include functions that may complyor be compatible with the OpenFlow™ Switch Specification Version 1.1.0Implemented (Wire Protocol 0x02) dated Feb. 28, 2011, and/or laterversions of this specification. In another embodiment, SB API 368 mayinclude custom and/or proprietary functions.

Turning again to FIG. 2, in some embodiments, host memory 214 mayinclude agent 252. Agent 252 is configured to provide customizationand/or update capability related to SAL 364 and SB API 368. For example,agent 252 may be utilized to push updates to SAL 364 and/or SB API 368.Updates may include updates to SAL 364, updates to SB API 368 and/orupdates to libraries 337. The updates may be provided, for example, bythe first NIC 316 OEM. In another example, agent 252 may be utilized topush custom modules, e.g., custom module(s) 372 a . . . 372 n, from aworkstation, e.g., workstation 110, to a network interface controller,e.g., first NIC 316. Agent 252 may be utilized to specify, modify and/orupdate configuration data related to SAL 364 and/or SB API 368.

FIG. 4 illustrates an example workstation 410 consistent with variousembodiments of the present disclosure. Workstation 410 is one example ofworkstation 110 of FIG. 1. Workstation 410 may be utilized by a user,e.g., a system administrator, to generate custom module(s) 424 and/orprotocols, e.g., a custom SB API. Workstation 410 includes a processor412, I/O circuitry 414, a user interface 416 and memory 418. Memory 418includes an operating system OS 420 and an integrated developmentenvironment IDE 422. IDE 422 may be used to generate one or more custommodule(s) 424. Custom module(s) 424 correspond to one or more of custommodule(s) 372 a, . . . , 372 n of FIG. 3.

Processor 412 is configured to perform operations of workstation 410.I/O circuitry 414 is configured to couple workstation 410 to computingdevice 102. In some embodiments, workstation 410 may be coupled tocomputing device 102 by network 104.

In some embodiments, workstation 410 may be directly coupled tocomputing device 102. User interface 416 may include, e.g., a keyboardand a display and is configured to allow the system administrator toaccess IDE 422, e.g., to generate and/or test, e.g., custom SB APIs,and/or network configurations.

The IDE 422 is related to hybrid SDN controller 120 and may be providedby, e.g., OEM of the network interface 116. IDE 422 may includelibraries 430, header files 432 and/or tools 434. Tools 434 may includea compiler, e.g., a cross compiler, configured to provide executablecustom module(s) 424. Libraries 430 may correspond to libraries 337 andmay include functional modules that may be utilized in generating custommodules and/or custom protocols.

Workstation 410 and IDE 422 are configured to enable a user, e.g., anetwork administrator, to generate custom modules and/or protocols,e.g., a custom SB API. The custom modules and/or protocols may then bepushed to a network interface, e.g., first NIC 316 using agent 252. Thecustom protocols may be embodied, for example, in one or more custommodule(s) 372 a, . . . , 372 n. The custom module(s) 372 a, . . . , 372n may then be pushed to first NIC 316 by, e.g., agent 252. In anembodiment, the custom module(s) 372 a, . . . , 372 n may then beutilized in place of and/or in addition to SB API 368. In anotherembodiment, the custom module(s) 372 a, . . . , 372 n may be utilized toimplement code changes (such as bug fixes) in the SAL 364.

In an embodiment, SAL 364 may be configured to generate a simulatedrepresentation of the physical network 367, e.g., in response to arequest from IDE 422. The request may include a change in configurationof the physical network 104. Modifications to control parameters, e.g.,network device setting(s), and/or custom module(s) 372 a, . . . , 372 nrelated to the requested change in configuration may be pushed to thefirst NIC 316 by agent 252. The SAL 364 may then be configured toexecute testing utilizing the simulated representation of the physicalnetwork 367. The SAL 364 may be configured to expose the simulatedrepresentation of the physical network 367 to the host 205 and therebyto IDE 422. SAL 364 may be configured to utilize one or more custommodule(s) 372 a, . . . , 372 n, e.g., that produced successfulsimulation results, in place of and/or in addition to SB API 368.

Thus, modifications to elements of the data plane, e.g., routingbehavior of one or more network device(s) 108 a, . . . , 108 n, may besimulated in the first NIC 316 using SAL 364 and the simulatedrepresentation of the physical network 367. The simulated representationof the physical network 367 may then appear to the host 205 and/or IDE422 as an actual representation of the physical network. In other words,it may be transparent to the host 205 whether the representation of thephysical network resides in the host 205 or resides in the first NIC316.

In some embodiments, depending on a capability of the first NIC 316, aplurality of simulated representations of the physical network may beresident on the first NIC 316. In these embodiments, processor 318 maycorrespond to a processor capable of virtualization. NIC memory 324 maythen include a virtual machine monitor (“hypervisor”) and each simulatedrepresentation of the physical network may be included in a respectiveSAL associated with a respective virtual machine. Each simulatedrepresentation of the physical network of the plurality of simulatedrepresentations of the physical network may be utilized by respectiveIDEs and associated network administrators.

Thus, IDE 422, agent 252 and SAL 364 are configured to providecustomization, simulation and test capabilities of a hybrid SDNcontroller consistent with various embodiments of the presentdisclosure. The simulated representation of the physical network 367 maybe exposed to the host 205 by SAL 364 resident in the first NIC 316.Custom module(s) 372 a, . . . , 372 n may be generated and tested and/orcontrol settings may be modified and tested prior to pushing them to theactual physical network 104.

In an embodiment, OS 360 may be configured to maintain a network stack361 related to operations of first NIC 316. The network stack 361 mayinclude routing tables and/or related network information. OS 360 and/orSAL 364 may then be configured to expose network data to, e.g., host 205based, at least in part, on the network stack 361 maintained by NIC OS360. The network data corresponds to network abstracting informationrelated to the representation of the physical network 366. For example,network data may include details of the network topology of physicalnetwork 104 related to nodes 106 a, . . . , 106 n and/or networkdevice(s) 108 a, . . . , 108 n, e.g., network configuration data (e.g.,number, type, location, settings, etc.).

Thus, OS 360 may be configured to maintain a network stack 361 relatedto the representation of the physical network 366 and the physicalnetwork 104. SAL 364 may utilize NIC network stack 361 to build therepresentation of the physical network 364. In other words, SAL 364 maybe configured to translate network data into a form appropriate for SDNcontroller functionality. The representation of the physical network 366may include, for example, a set of objects and/or entries in a database,that are related to the node(s) 106 a, . . . , 106 n and/or networkdevices(s) 108 a, . . . , 108 n and their configuration (e.g., controlsettings). SAL 364 may be further configured to translate the set ofobjects and/or entries in the database into a target format and tocommunicate the translated network data to, e.g., the host 205 and SDNmodules 236. For example, the target format may include data formatsused by web services (i.e., a software system designed to supportinteroperable machine-to-machine interaction over a network). The dataformats may include XML (eXtensible Markup Language), JSON (JavaScriptObject Notation) and/or SOAP (Simple Object Access Protocol). XML is amarkup language that defines a set of rules for encoding documents in aformat that is both human-readable and machine-readable. XML may complyor be compatible with World Wide Web Consortium (“W3C”) recommendation,titled “Extensible Markup Language (XML) 1.0 (Fifth Edition)”, releasedNov. 26, 2008 and/or later versions of this recommendation. JSON is adata-interchange format that is based on a subset of the JavaScriptProgramming Language, Standard ECMA-262 3rd Edition—December 1999. SOAPis a protocol intended for exchanging structured information in adecentralized, distributed environment. SOAP uses XML technologies todefine an extensible messaging framework configured to provide a messageconstruct that can be exchanged over a variety of underlying protocols.SOAP may comply or be compatible with W3C recommendation, titled “SOAPVersion 1.2 Part 1: Messaging Framework (Second Edition)”, released Apr.27, 2007 and/or later versions of this recommendation. In anotherexample, the target format may correspond to MIBS (managementinformation base) associated with SNMP (Simple Network ManagementProtocol). In another example, the target format may correspond to acustom format (e.g., interface) selected by e.g., a networkadministrator and defined by, e.g., IDE 422. The translated network datamay generally include capabilities of each network device 108 a, . . . ,108 n and may further include configuration settings associated witheach network device 108 a, . . . , 108 n. In some embodiments, thetranslated network data may include network topology changes related tonode(s) 106 a, . . . , 106 n.

In an embodiment, first NIC 316 may be configured to process receivednetwork packets and/or frames that include, e.g., messages and/or data.The received network packets and/or frames may be forwarded to the host,e.g., host 205, without modification, may be modified and then forwardedto host 205 or may not be forwarded to host 205 at all. For example, MAC322 may be configured to receive network traffic including any packet(i.e., all packets) from the physical network 104. SAL 364 may then beconfigured to determine a status of the physical network 104 and/orwhether the physical network topology has changed based, at least inpart, on inspection of the received packets, i.e., the network traffic.Network topology changes may include one or more node(s), e.g., node(s)106 a, . . . , 106 n, coupling to or decoupling from the physicalnetwork 104, a change in location of a node, link status changes and/ornew services being deployed in node(s). Network status may includequality of service, error rate, status information and/or generally anychange in resources related to network device(s) 108 a, . . . , 108 n.SAL 364 may be configured to forward information related to physicalnetwork 104 status and/or topology changes to host 205 and to SDNmodules 236. Thus, physical network 104 status and/or topology changedeterminations may be performed by first NIC 316.

In another embodiment, host interface 320 (and MAC 321) may beconfigured to forward any packets received from the host 205 to MAC 322for transmission onto the physical network 104. Any useful informationincluded in the packets from host 205 may then be extracted by, e.g.,SAL 364. Useful information includes any SDN-related information, e.g.,messages to the SB API 368. The useful information may then beinterpreted and, utilized to manipulate, e.g., the representation of thephysical network 366.

Thus, the SAL 364 may be configured to monitor network operation byconfiguring MAC 322 to receive all network traffic (i.e., “promiscuousmode”) and/or monitoring packets (e.g., messages) from the host 205 to,e.g., SB API 368. The SAL 364 may be further configured to selectivelyforward information related to network status and/or configuration tohost 205 and/or to update the physical representation of the network 366based, at least in part, on the monitored packets. Thus, capabilities ofthe first NIC 316 may be exploited to support SDN functionality ofhybrid SDN controller that includes host SDN modules 236 and NIC SDNmodules 362.

In an embodiment, host 205 may include a complete network stack 231. Thenetwork stack 231 may include routing tables and/or related networkinformation. In this embodiment, network data may be maintained by thehost 205. A network interface, e.g., first NIC 316 and, e.g., SAL 364may be configured to communicate network status and/or configurationchanges to host 205, e.g., OS 230 and/or SDN modules 236. Modificationsto physical network 104 communicated to host 205 may then result inupdating of network stack 231. In another embodiment, network stack 231may correspond to a relatively limited stack. In this embodiment, OS 230may include a software framework configured for efficient and relativelyfast packet processing. For example, the software framework may complyor be compatible with the Data Plane Development Kit (DPDK) configuredto optimize packet processing on Intel® Architecture processors. Ofcourse, the Intel® Architecture is only an example implementation and,in other embodiments, the teachings presented herein may be used forother core architecture technologies as may be provided by, for example,Motorola®, Apple®, . . . etc. In both embodiments, processing load onhost processor 210 related to packet processing may be generally limitedsince first NIC 316 (and SAL 364) may be configured to communicate onlymodifications (i.e., changes) to the physical network 104. Debugging mayalso be facilitated by configuring, e.g., MAC 322, to monitor allnetwork traffic (i.e., promiscuous mode), as described herein.

Thus, a first portion of a hybrid SDN controller consistent with variousembodiments of the present disclosure may be implemented on a host,e.g., host 205, of a computing device, and a second portion of thehybrid SDN controller may be implemented on a network interfacecontroller, e.g., first NIC 316, included in the computing device. Thefirst portion may include host SDN modules 236 (e.g., NB API 240,network service functions 242, network orchestration functions 244 andnetwork management functions 246). The second portion may include theSAL 364 including the representation of the physical network 366, SB API368 and/or one or more custom module(s) 372 a, . . . , 372 n configuredto communicate with (e.g., control) network device(s) 108 a, . . . 108 nincluded in physical network 104. First NIC 316, utilizing e.g., MAC 322and/or host interface 320 (and MAC 321), may be configured to monitornetwork traffic and/or packets to be transmitted and to detect physicalnetwork 104 status and/or modifications to the physical network 104topology. SAL 364 may then update the physical representation of thenetwork 366 and may communicate the status and/or modification to host205. SAL 364 and/or SB API 368 may be efficiently coded by or on behalfof, e.g., the first NIC 316 OEM. Processing load on host processor 210may this be reduced.

FIG. 5 illustrates another example network interface controller, e.g.,standard network interface controller 516, consistent with oneembodiment of the present disclosure. The standard network interfacecontroller 516 may have relatively less functionality compared to firstNIC 316. The standard network interface controller 516 may be generallyconfigured to perform at least some network interface functions for ahybrid SDN controller, e.g., hybrid SDN controller 120. The standardnetwork interface controller 516 may include processor circuitry 518configured for relatively limited functionality. Processor circuitry 518may include, for example, a microcontroller, a microengine, anapplication-specific integrated circuit (ASIC), a field programmablegate array (FPGA) and/or any other controller circuitry that isgenerally capable of performing typical network interface controllerand/or packet processing functions. For example, a microengine mayinclude a programmable microcontroller. The standard network interfacecontroller 516 may include a direct memory access (DMA) interface 520configured to facilitate transfer of commands and/or data betweenstandard network interface controller 516 and a host, e.g., host 205,and a medium access controller MAC 522 and PHY 523 configured to couplea computing device, e.g., computing device 102, to network 104.

The standard network interface controller 516 may include limitedstorage 524 configured to store a boot module 530 configured to boot theprocessor 518 and an SDN engine 532 configured to initiate operations ofa limited SAL 526. Communication between SAL 526 and a host, e.g., host205, may be performed through, e.g., DMA (Direct Memory Access)/PCIetransactions by DMA host interface 520. Standard network interfacecontroller 516 may be further configured to utilize I/O memory and/orqueues that a NIC driver in a host may also be utilizing, e.g., I/Omemory 218, queue(s) 220 and NIC driver 216 of FIG. 2. The limited SAL526 may be configured to utilize the I/O memory 218 and/or queues 220 toexchange network-related data with the host 205. Network-related datamay include, e.g., network topology (configuration) updates such as achange in state of a node, addition of a node, exit of a node, etc.Network-related data may further include an identifier that correspondsto which SB API, e.g., SB API 534, and/or custom module, e.g., custommodule 536, may be active. Thus, the host 205 and standard networkinterface controller 516 may be sharing a memory map in order toexchange data.

Limited SAL 526 may be implemented as tables in, e.g., circuitry.Limited SAL 526 may be further configured to utilize a processing unitand/or pipeline in order to manipulate the data stored in the tables andto create the PCIe transactions. Standard network interface controller516 may be configured to store limited SB API 534. Thus, in thisembodiment, limited SAL 526 and limited SB API 534 functionality may beincluded in standard network interface controller 516. The limitationsare related to capability available on the standard network interfacecontroller 516.

Thus, a hybrid SDN controller may be configured with SDN controllerfunctionality distributed between a host and a network interfacecontroller of a computing device. A first portion of a hybrid SDNcontroller consistent with various embodiments of the present disclosuremay be implemented in a host included in the computing device. The firstportion of the hybrid SDN controller may include northbound API, networkservice functions, network orchestration functions and networkmanagement functions. A second portion of the hybrid SDN controller maybe implemented in a network interface controller included in thecomputing device. The second portion of the hybrid SDN controller mayinclude a southbound API and a service abstraction layer module thatincludes a representation of the physical network.

The service abstraction layer and southbound API may be efficientlycoded. Implementing the service abstraction layer and southbound API onthe network interface is configured to reduce processing load on thehost. Networking logic (e.g., network service functions, networkorchestration functions and network management functions) may continueto be coded in the high level object oriented language without affectingthe network interface programming. Distributing the SDN controlfunctions between the host and the network interface is configured to betransparent to applications utilizing the hybrid SDN controllerfunctionality.

FIG. 6 illustrates a flowchart 600 of example operations of a hybridsoftware-defined networking (SDN) controller consistent with anembodiment of the present disclosure. The operations may be performed,for example, by first NIC 316, host 205 and/or workstation 410. Inparticular, flowchart 600 depicts example operations configured togenerate and expose a representation of a physical network and asimulated representation of the physical network.

Program flow may begin at operation 602. Operation 602 includesimplementing a service abstraction layer module (SAL) on a networkinterface controller. A representation of a physical network may begenerated, e.g., by the SAL, at operation 604. Operation 606 may includeexposing the representation of the network to a host. Operation 608 mayinclude requesting, e.g., by a workstation, a change in a configurationof the physical network. A simulated representation of the network,based at least in part, on the requested change, may be generated atoperation 610. Operation 612 may include exposing the simulatedrepresentation of the network to the host. For example, the simulatedrepresentation may be exposed by the SAL.

FIG. 7 illustrates a flowchart 700 of example operations of a hybrid SDNcontroller consistent with an embodiment of the present disclosure. Theoperations may be performed, for example, by workstation 410, host 205and/or network interface controller 316. In particular, flowchart 700depicts example operations configured to generate a custom module and toaccess a network with the custom module.

Program flow may begin at operation 702. Operation 702 includesgenerating a custom module. For example, the custom module may begenerated by a workstation coupled to a computing device, e.g.,computing device 102. The custom module may be provided to the networkinterface controller at operation 704. For example, an agent 252 in ahost may configured to provide the custom module to the NIC. Operation706 may include accessing the physical network using the custom module.

FIG. 8 illustrates a flowchart 800 of example operations of a hybrid SDNcontroller consistent with an embodiment of the present disclosure. Theoperations may be performed, for example, by a network interfacecontroller and/or a host. In particular, flowchart 800 depicts exampleoperations configured to determine whether a physical network topologyhas changed based, at least in part, on analysis of network traffic.Operation 802 includes monitoring network traffic on the physicalnetwork. For example, the network interface controller may be configuredto monitor network traffic. Operation 804 may include determiningwhether a physical network topology has changed based, at least in parton, network traffic. Operation 806 includes communicating a change inphysical network topology to a host in a format selected by the host.For example, a service abstraction layer module, e.g., SAL 364, includedin the network interface controller may be configured to translate achange in physical network topology from the format of the physicalrepresentation of the network 366 included in the SAL 364 to a dataformat used by, e.g., web services.

While FIGS. 6, 7 and 8 illustrate various operations according to anembodiment, it is to be understood that not all of the operationsdepicted in FIGS. 6, 7 and/or 8 are necessary for other embodiments.Indeed, it is fully contemplated herein that in other embodiments of thepresent disclosure, the operations depicted in FIGS. 6, 7 and/or 8and/or other operations described herein may be combined in a manner notspecifically shown in any of the drawings, but still fully consistentwith the present disclosure. Thus, claims directed to features and/oroperations that are not exactly shown in one drawing are deemed withinthe scope and content of the present disclosure.

The foregoing provides example system architectures and methodologies,however, modifications to the present disclosure are possible. The hostprocessor may include one or more processor cores and may be configuredto execute system software. System software may include, for example, anoperating system. Host memory may include I/O memory buffers configuredto store one or more data packets that are to be transmitted by, orreceived by, a network interface.

The operating system (OS) may be configured to manage system resourcesand control tasks that are run on, e.g., host 205, first NIC 316 and/orworkstation 410. For example, the OS may be implemented using MicrosoftWindows, HP-UX, Linux, or UNIX, although other operating systems may beused. In some embodiments, the OS may be replaced by a virtual machinemonitor (or hypervisor) which may provide a layer of abstraction forunderlying hardware to various operating systems (virtual machines)running on one or more processing units. The operating system and/orvirtual machine may implement one or more protocol stacks. A protocolstack may execute one or more programs to process packets. An example ofa protocol stack is a TCP/IP (Transport Control Protocol/InternetProtocol) protocol stack comprising one or more programs for handling(e.g., processing or generating) packets to transmit and/or receive overa network.

The host and or network interface controller memory may comprise one ormore of the following types of memory: semiconductor firmware memory,programmable memory, non-volatile memory, read only memory, electricallyprogrammable memory, random access memory, flash memory, magnetic diskmemory, and/or optical disk memory. Either additionally or alternativelysystem memory may comprise other and/or later-developed types ofcomputer-readable memory.

Embodiments of the operations described herein may be implemented in asystem that includes one or more storage devices having stored thereon,individually or in combination, instructions that when executed by oneor more processors perform the methods. The processors may include, forexample, a processing unit and/or programmable circuitry in the host 205and/or other processing unit or programmable circuitry in the first NIC316 and/or the workstation 410. Thus, it is intended that operationsaccording to the methods described herein may be distributed across aplurality of physical devices, such as processing structures at severaldifferent physical locations. The storage device may include any type oftangible, non-transitory storage device, for example, any type of diskincluding floppy disks, optical disks, compact disk read-only memories(CD-ROMs), compact disk rewritables (CD-RWs), and magneto-optical disks,semiconductor devices such as read-only memories (ROMs), random accessmemories (RAMs) such as dynamic and static RAMs, erasable programmableread-only memories (EPROMs), electrically erasable programmableread-only memories (EEPROMs), flash memories, magnetic or optical cards,or any type of storage devices suitable for storing electronicinstructions.

“Circuitry”, as used in any embodiment herein, may comprise, forexample, singly or in any combination, hardwired circuitry, programmablecircuitry, state machine circuitry, and/or firmware that storesinstructions executed by programmable circuitry. “Module”, as usedherein, may comprise, singly or in any combination circuitry and/or codeand/or instructions sets (e.g., software, firmware, etc.).

In some embodiments, a hardware description language may be used tospecify circuit and/or logic implementation(s) for the various modulesand/or circuitry described herein. For example, in one embodiment thehardware description language may comply or be compatible with a veryhigh speed integrated circuits (VHSIC) hardware description language(VHDL) that may enable semiconductor fabrication of one or more circuitsand/or modules described herein. The VHDL may comply or be compatiblewith IEEE Standard 1076-1987, IEEE Standard 1076.2, IEEE1076.1, IEEEDraft 3.0 of VHDL-2006, IEEE Draft 4.0 of VHDL-2008 and/or otherversions of the IEEE VHDL standards and/or other hardware descriptionstandards.

Physical network 104 may comprise a packet switched network. Networkinterface controller 316, 516 may be capable of communicating withnode(s) 106 a, . . . , 106 n and/or network device(s) 108 a, . . . , 108n using a selected packet switched network communications protocol. Oneexample communications protocol may include an Ethernet communicationsprotocol which may be capable permitting communication using aTransmission Control Protocol/Internet Protocol (TCP/IP). The Ethernetprotocol may comply or be compatible with the Ethernet standardpublished by the Institute of Electrical and Electronics Engineers(IEEE) titled “IEEE 802.3 Standard”, published in December, 2008 and/orlater versions of this standard. Alternatively or additionally, networkinterface controller 316, 516 may be capable of communicating withnode(s) 106 a, . . . , 106 n and/or network device(s) 108 a, . . . , 108n, using an X.25 communications protocol. The X.25 communicationsprotocol may comply or be compatible with a standard promulgated by theInternational Telecommunication Union-Telecommunication StandardizationSector (ITU-T). Alternatively or additionally, network interfacecontroller 316, 516 may be capable of communicating with node(s) 106 a,. . . , 106 n and/or network device(s) 108 a, . . . , 108 n using aframe relay communications protocol. The frame relay communicationsprotocol may comply or be compatible with a standard promulgated byConsultative Committee for International Telegraph and Telephone (CCITT)and/or the American National Standards Institute (ANSI). Alternativelyor additionally, network interface controller 316, 516 may be capable ofcommunicating with node(s) 106 a, . . . , 106 n and/or network device(s)108 a, . . . , 108 n, using an Asynchronous Transfer Mode (ATM)communications protocol. The ATM communications protocol may comply orbe compatible with an ATM standard published by the ATM Forum titled“ATM-MPLS Network Interworking 1.0” published August 2001, and/or laterversions of this standard. Of course, different and/or after-developedconnection-oriented network communication protocols are equallycontemplated herein.

Thus, a hybrid SDN controller consistent with various embodiments of thepresent disclosure is configured to distribute SDN controllerfunctionality between a host and a network interface of a computingdevice, e.g., a server. A first portion of a hybrid SDN controllerconsistent with various embodiments of the present disclosure isconfigured to be implemented on the host. The first portion may includenorthbound Application Programming Interface(s) (API(s)) and networkinglogic including network service functions, network orchestrationfunctions and network management functions. The second portion of thehybrid SDN controller is configured to be implemented on the networkinterface controller. The second portion may include a southbound APIand a service abstraction layer (e.g., SAL module) that includes arepresentation of the physical network.

Thus, a network interface consistent with various embodiments of thepresent disclosure is configured as a functional unit that includesnetwork interface functionality as well as the portion of the hybrid SDNcontroller that includes the service abstraction layer and thesouthbound API. The service abstraction layer and southbound API may beefficiently coded. In some embodiments, custom module(s) related to thesouthbound API may be implemented by an enterprise. Implementing theservice abstraction layer and southbound API on the NIC is furtherconfigured to reduce processing load on the host. Networking logic maycontinue to be coded in the high level object oriented language withoutaffecting the NIC programming. Distributing the SDN control functionsbetween the host and the NIC is configured to be transparent to anapplication executing on a node in the physical network.

Accordingly, the present disclosure provides an example networkinterface controller. The example network interface controller includesa portion of a hybrid software-defined networking (“SDN”) controller,the portion of the hybrid SDN controller including a service abstractionlayer module (“SAL”) and a southbound application programming interface(“SB API”), the SAL including a representation of a physical network.

The present disclosure also provides an example method. The examplemethod includes implementing a service abstraction layer module (“SAL”)on a network interface controller; generating, by the SAL, arepresentation of a physical network; and exposing, by the SAL, therepresentation of the physical network to a host.

The present disclosure also provides an example computing device. Theexample computing device includes a host and a network interfacecontroller. The host includes a first portion of a hybridsoftware-defined networking (“SDN”) controller, the first portion of thehybrid SDN controller including a plurality of SDN modules and anorthbound application programming interface (“API”). The networkinterface controller includes a second portion of the hybrid SDNcontroller, the second portion of the hybrid SDN controller including aservice abstraction layer module (“SAL”) and a southbound applicationprogramming interface (“SB API”), the SAL including a representation ofa physical network.

The present disclosure also provides an example system that includes oneor more storage devices having stored thereon, individually or incombination, instructions that when executed by one or more processorsresult in the following operations including: implementing a serviceabstraction layer module (“SAL”) in a network interface controller;generating a representation of a physical network; and exposing therepresentation of the physical network to a host.

The terms and expressions which have been employed herein are used asterms of description and not of limitation, and there is no intention,in the use of such terms and expressions, of excluding any equivalentsof the features shown and described (or portions thereof), and it isrecognized that various modifications are possible within the scope ofthe claims. Accordingly, the claims are intended to cover all suchequivalents.

Various features, aspects, and embodiments have been described herein.The features, aspects, and embodiments are susceptible to combinationwith one another as well as to variation and modification, as will beunderstood by those having skill in the art. The present disclosureshould, therefore, be considered to encompass such combinations,variations, and modifications.

What is claimed is:
 1. A network interface controller (NIC) to couple toa host computing device, the NIC comprising: a host interface to coupleto the host computing device; a hybrid software-defined networking (SDN)controller implemented in circuitry of the NIC and configured to performat least one SDN control function to reduce SDN processing load on thehost computing device, the hybrid SDN controller comprising: a serviceabstraction layer module (SAL); a network stack; and a southboundapplication programming interface (SB API); wherein: the SAL isconfigured, in response to a request including a change in configurationof a physical network, to provide a simulated representation of thephysical network based at least in part on the network stack and thechange in configuration included in the request, to execute testingutilizing the simulated representation of the physical network, and toexpose the simulated representation of the physical network to the hostcomputing device as an actual representation of the physical network. 2.The NIC of claim 1, wherein the hybrid SDN controller further comprisesa custom module, the custom module corresponding to a custom applicationprogramming interface (“API”).
 3. The NIC of claim 1, wherein the hostinterface implements Peripheral Component Interconnect Express (PCIe)communications protocol to communicate with the host computing device.4. The NIC of claim 1 wherein the SAL is configured to translate networkdata into a form appropriate for SDN controller functionality.
 5. TheNIC of claim 1 wherein the representation of the physical networkincludes a set of objects and/or entries in a database.